Not in practice, it won't. Such discussion tends to attract kiddies who are more interested in exploiting such things.
If you want to motivate people to write less crappy software, discuss techniques to write good software and find constructive ways to motivate developers to use them.
The basic problem is that exploiting security holes is a relatively easy task with highly visible satisfaction and payoff for the people inclined to exploit them. It is an activity that appeals to the less altruistic and more selfish people in the world, and has a low bar to entry. [There are exceptions to that statement, but you won't find many talented people who exploit security holes for altruistic reasons in the open on a forum like this].
In contrast, writing good software is a technically challenging task that, if done well, does not give overt benefits or satisfaction for the developer. If their job is done right, it's just "what was expected". If they mess up in good faith, they get caned for it. That combination of being taken for granted if you do your job properly, but crucified whenever you make honest mistakes, is virtually guaranteed to demotivate people from doing a good job. It is easier to keep one's head below the parapet, do a mediocre job, and leave someone else to clean up the resultant mess.